Business Assistant

home *** CD-ROM | disk | FTP | other *** search

/ Business Assistant / Business Assistant.iso / indus / eztime / eztime.lzh / EZTIME.DOC next >

Wrap

Text File | 1992-04-06 | 186KB | 8,053 lines

R E S T A U R A N T M A N A G E M E N T S Y S T E M S E Z T I M E U S E R ' S G U I D E V2.0 by Gary A. Kunkel All rights reserved Proprietary Notice RMS EZTIME is a proprietary product written by Gary A. Kunkel and is being distributed by Restaurant Management Systems of Irving, Texas. Restaurant Management Systems P.O. Box 171515 Irving, TX 75017-1515 (214) 986-6581 D I S T R I B U T I O N N O T I C E _________________________________________________________________ RMS is distributing this software by way of the "SHAREWARE" concept. If, after trying the product, you decide to use it, send $99.00 payment for a single user license, or $149.00 for a network license. This will make you a "registered" user. All registered owners will receive a bound copy of the User Guide that contains all information in this disk version of the manual, plus more. Registered owners are notified of all future releases, have access to technical support, and have input into future versions of the software. If, after all this, you still decide not to send the payment, you are still encouraged to copy and distribute this software with your peers with the following restrictions: 1. The software is distributed as a complete set. Do not alter, or delete any program files from the distribution copies. 2. No charge is to be made for copying or distributing the software. User Groups may make a small charge to cover the cost of disks and copying. This charge is not to exceed $15.00. 3. Commercial sale of EZTIME in any manner is prohibited without RMS's written permission. Copyright (C) 1989-1991 Restaurant Management Systems LIMITED WARRANTY _________________________________________________________________ This system is provided "as is" without warranty of any kind, express or implied, including, but not limited to the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the system is with you, the purchaser. Should the program prove defective, you assume the entire cost of all necessary servicing, repair, or correction. In no event will Restaurant Management Systems or Gary A. Kunkel be liable to you for any damages, including any lost profits, lost savings, or other incidental or consequential damages arising out of the use or inability to use such system even if RMS or an authorized RMS agent has been advised of the possibility of such damages, or for any claim by any other party. PC-DOS is a trademark of International Business Machines OS/2 is a trademark of International Business Machines D-Base IV is a trademark of Borland International Object Vision is a trademark of Borland International Q&A Database Editor is a trademark of Pioneer Software DR-DOS is a trademark of Digital Research MS-DOS is a trademark of Microsoft Corporation Microsoft Windows is a trademark of Microsoft Corporation Copyright (C) 1989-1991 Restaurant Management Systems TABLE OF CONTENTS i _________________________________________________________________ 1 System Overview Introduction . . . . . . . . . . . . . . . . . . . . . . 1 Functional Overview . . . . . . . . . . . . . . . . . . . 1 Labor Activity Theory . . . . . . . . . . . . . . . . . . 2 Military Time . . . . . . . . . . . . . . . . . . . . . . 3 Historical Databases and Decision Support . . . . . . . . 4 Coupon Drop Tracking . . . . . . . . . . . . . . . . . . 4 2 Getting Started System Installation . . . . . . . . . . . . . . . . . . . 5 System Requirements . . . . . . . . . . . . . . . . . . . 5 Installing Software . . . . . . . . . . . . . . . . . . . 6 Loading Reference Tables . . . . . . . . . . . . . . . . 7 Copyright (C) 1989-1991 Restaurant Management Systems TABLE OF CONTENTS ii _________________________________________________________________ 3 Using Browse Learning Browse . . . . . . . . . . . . . . . . . . . . . 8 Manual Conventions . . . . . . . . . . . . . . . . . . . 8 Basic Terms and Operations . . . . . . . . . . . . . . . 8 File . . . . . . . . . . . . . . . . . . . . . . . . . 9 Database . . . . . . . . . . . . . . . . . . . . . . . 9 Record . . . . . . . . . . . . . . . . . . . . . . . . 9 Index File . . . . . . . . . . . . . . . . . . . . . . 9 Window . . . . . . . . . . . . . . . . . . . . . . . . 9 Browse Function . . . . . . . . . . . . . . . . . . . . 10 Current Record . . . . . . . . . . . . . . . . . . . . 10 Menu . . . . . . . . . . . . . . . . . . . . . . . . . 10 Command Entry . . . . . . . . . . . . . . . . . . . . . 11 Escape <ESC> Key . . . . . . . . . . . . . . . . . . . 11 Entry Areas . . . . . . . . . . . . . . . . . . . . . . 11 Menu Selections . . . . . . . . . . . . . . . . . . . . 13 Scrolling . . . . . . . . . . . . . . . . . . . . . . . 14 Page Down . . . . . . . . . . . . . . . . . . . . . . . 14 Page Up . . . . . . . . . . . . . . . . . . . . . . . . 14 Down Arrow . . . . . . . . . . . . . . . . . . . . . . 14 Up Arrow . . . . . . . . . . . . . . . . . . . . . . . 14 Top . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Bottom . . . . . . . . . . . . . . . . . . . . . . . . 14 Help . . . . . . . . . . . . . . . . . . . . . . . . . 15 Modify Menu . . . . . . . . . . . . . . . . . . . . . . 15 Modify Record . . . . . . . . . . . . . . . . . . . . . 15 Delete Record . . . . . . . . . . . . . . . . . . . . . 15 Undelete Record . . . . . . . . . . . . . . . . . . . . 15 Add Blank Record . . . . . . . . . . . . . . . . . . . 16 Add Copy Record . . . . . . . . . . . . . . . . . . . . 16 Position Menu . . . . . . . . . . . . . . . . . . . . . 16 Find . . . . . . . . . . . . . . . . . . . . . . . . . 17 Select Record Ordering Index . . . . . . . . . . . . . 18 Edit / Browse Switch . . . . . . . . . . . . . . . . . 18 Exiting Browse . . . . . . . . . . . . . . . . . . . . 18 Copyright (C) 1989-1991 Restaurant Management Systems TABLE OF CONTENTS iii _________________________________________________________________ 4 System Functions Main Menu . . . . . . . . . . . . . . . . . . . . . . . 19 Main Menu - Update Reference Tables . . . . . . . . . . 19 Main Menu - Post Employee Time Records . . . . . . . . 20 Main Menu - Run Dayend Processes . . . . . . . . . . . 20 Main Menu - Generate Reports . . . . . . . . . . . . . 21 Main Menu - Export Payroll Data . . . . . . . . . . . . 21 Main Menu - Browse History Files . . . . . . . . . . . 21 Main Menu - Print Registration Request Form . . . . . . 22 Main Menu - Print User Guide . . . . . . . . . . . . . 22 Main Menu Exit . . . . . . . . . . . . . . . . . . . . 22 Activity Code Table Maintenance . . . . . . . . . . . . 23 Coupon Area Code Table Maintenance. . . . . . . . . . . 25 Employee Classes Table Maintenance . . . . . . . . . . 26 Employee Master Table Maintenance . . . . . . . . . . . 27 System Setup Table Maintenance . . . . . . . . . . . . 29 Pack Reference Tables . . . . . . . . . . . . . . . . . 32 Post Daily Time Records . . . . . . . . . . . . . . . . 33 Dayend . . . . . . . . . . . . . . . . . . . . . . . . 36 Database Backup . . . . . . . . . . . . . . . . . . . . 36 Recover a Previous Days Backup . . . . . . . . . . . . 36 Backup Process Modifications . . . . . . . . . . . . . 37 System Backup . . . . . . . . . . . . . . . . . . . . . 37 Nightly Batch Process . . . . . . . . . . . . . . . . . 37 Reports . . . . . . . . . . . . . . . . . . . . . . . . 38 Report - Labor Usage by Activity Code . . . . . . . . . 38 Report - Coupon Drop Report . . . . . . . . . . . . . . 38 Report - Daily Labor Detail Report . . . . . . . . . . 38 Report - Daily Labor Forecast by Activity Code . . . . 39 Report - Daily Labor Forecast by Activity Type . . . . 39 Export Payroll Data to File . . . . . . . . . . . . . . 40 Report - Produce Payroll Report . . . . . . . . . . . . 40 Browse History Tables . . . . . . . . . . . . . . . . . 41 History Browse - Hourly Labor History . . . . . . . . . 41 History Browse - Activity History . . . . . . . . . . . 41 History Browse - Employee Time Records . . . . . . . . 41 History Browse - Coupon Drop History . . . . . . . . . 41 5 Adhoc Reporting and System Customization Requests AdHoc Reporting Requirements . . . . . . . . . . . . . 42 System Modification Warning . . . . . . . . . . . . . . 42 System Modification Requests . . . . . . . . . . . . . 42 Copyright (C) 1989-1991 Restaurant Management Systems TABLE OF CONTENTS iv _________________________________________________________________ 6 Data Dictionary Tables . . . . . . . . . . . . . . . . . . . . . . . . 43 Indexes . . . . . . . . . . . . . . . . . . . . . . . . 43 Field Listing by Table . . . . . . . . . . . . . . . . 44 Activity Code . . . . . . . . . . . . . . . . . . . . . 46 Activity Description . . . . . . . . . . . . . . . . . 47 Activity Type . . . . . . . . . . . . . . . . . . . . . 48 Employee Class Code . . . . . . . . . . . . . . . . . . 49 Employee Class Description . . . . . . . . . . . . . . 50 Clock In Date . . . . . . . . . . . . . . . . . . . . . 51 Clock In Time . . . . . . . . . . . . . . . . . . . . . 52 Clock Out Date . . . . . . . . . . . . . . . . . . . . 53 Clock Out Time . . . . . . . . . . . . . . . . . . . . 54 Coupon Area Code . . . . . . . . . . . . . . . . . . . 55 Coupon Area Code Description . . . . . . . . . . . . . 56 Coupon Drop Cost . . . . . . . . . . . . . . . . . . . 57 Coupons Hung . . . . . . . . . . . . . . . . . . . . . 58 Coupon Unit Cost . . . . . . . . . . . . . . . . . . . 59 Coupon Processing Switch . . . . . . . . . . . . . . . 60 Driver's License Number . . . . . . . . . . . . . . . . 61 Employee Address . . . . . . . . . . . . . . . . . . . 62 Employee City . . . . . . . . . . . . . . . . . . . . 63 Employee Name . . . . . . . . . . . . . . . . . . . . 64 Employee Number . . . . . . . . . . . . . . . . . . . . 65 Employee Phone Number . . . . . . . . . . . . . . . . . 66 Employee Postal Code . . . . . . . . . . . . . . . . . 67 Employee State . . . . . . . . . . . . . . . . . . . . 68 Employee Status . . . . . . . . . . . . . . . . . . . 69 Employee Wage . . . . . . . . . . . . . . . . . . . . 70 Labor Cost 1 through 30 . . . . . . . . . . . . . . . 71 Hours Worked 1 through 30 . . . . . . . . . . . . . . . 72 Labor Goal . . . . . . . . . . . . . . . . . . . . . . 73 Lunch Hours Worked . . . . . . . . . . . . . . . . . . 74 Lunch Hour Minutes Worked . . . . . . . . . . . . . . 75 Lunch Hour Pay . . . . . . . . . . . . . . . . . . . . 76 Lunch Hour Stop Time . . . . . . . . . . . . . . . . . 77 Lunch Hour Start Time . . . . . . . . . . . . . . . . . 78 Over Time Code . . . . . . . . . . . . . . . . . . . . 79 Over Time Code Description . . . . . . . . . . . . . . 80 Over Time Reset Days . . . . . . . . . . . . . . . . . 81 Over Time Hours . . . . . . . . . . . . . . . . . . . 82 Over Time Hours Calc Start . . . . . . . . . . . . . . 83 Copyright (C) 1989-1991 Restaurant Management Systems TABLE OF CONTENTS v _________________________________________________________________ 6 Data Dictionary (continued) Over Time Minutes Worked . . . . . . . . . . . . . . . 84 Over Time Pay . . . . . . . . . . . . . . . . . . . . 85 Over Time Pay Period Begin Date . . . . . . . . . . . . 86 Over Time Pay Period End Date . . . . . . . . . . . . . 87 Overtime Processing Switch . . . . . . . . . . . . . . 88 Employee Over Under Amount . . . . . . . . . . . . . . 89 Period Start Date . . . . . . . . . . . . . . . . . . 90 Period Stop Date . . . . . . . . . . . . . . . . . . . 90 Pay Period Minutes To Date . . . . . . . . . . . . . . 91 Process 1 through 5 . . . . . . . . . . . . . . . . . . 92 History File Purge Days . . . . . . . . . . . . . . . . 93 Standard Pay . . . . . . . . . . . . . . . . . . . . . 94 Standard Hour Hours Worked . . . . . . . . . . . . . . 95 Standard Minutes Worked . . . . . . . . . . . . . . . . 96 Store Date . . . . . . . . . . . . . . . . . . . . . . 97 Store Number . . . . . . . . . . . . . . . . . . . . . 98 Standard Pay . . . . . . . . . . . . . . . . . . . . . 99 Total Hours . . . . . . . . . . . . . . . . . . . . . 100 Total Pay . . . . . . . . . . . . . . . . . . . . . . 101 User Text 1 . . . . . . . . . . . . . . . . . . . . . 102 User Text 2 . . . . . . . . . . . . . . . . . . . . . 102 7 Sample Reports Labor Usage by Activity Code (Labor Activity Report). . 103 Coupon Drop Report . . . . . . . . . . . . . . . . . . 104 Daily Labor Detail Report . . . . . . . . . . . . . . . 105 Daily Labor Forecast by Activity Code (Shift Sheet) . . 106 8 Appendix Browse Quick Reference . . . . . . . . . . . . . . . . 107 Daily Operational Procedures Worksheet . . . . . . . . 108 Error Messages . . . . . . . . . . . . . . . . . . . . 109 Order Form . . . . . . . . . . . . . . . . . . . . . . 112 Request to be put on Mailing List . . . . . . . . . . . 113 Customer Feedback . . . . . . . . . . . . . . . . . . . 114 Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM OVERVIEW 1 _________________________________________________________________ INTRODUCTION Restaurant Management System's (RMS) EZTIME is a powerful and cost effective tool for helping in the management of restaurants. This system will help a restaurant control its daily labor costs and improve customer service by providing an automated forecast of daily and hourly labor requirements. Additionally, it reduces manual bookkeeping requirements and provides management decision making reports. This system is intended to simplify, speed up and ensure the accuracy of the manager's daily, weekly and monthly tasks related to the management of human resources. For daily operations, the system was designed to be simple to operate. However, the initial install of the software requires careful thought in order to provide maximum long term benefit. This system was designed using the relational database model and modern day software engineering techniques. Careful attention has been placed on the overall construction of the system to make it simple to operate on a day to day basis. As you become a more sophisticated user, you will appreciate the open design of the system. The system is implemented on the industry standard DBASE IV file structure to allow for future user defined reporting requirements. FUNCTIONAL OVERVIEW The system will help establish better control over the following areas: 1) The system decreases manual book-keeping requirements by automating labor tracking and cost reporting. 2) The system provides improved monitoring of labor usage on a daily and hourly basis by labor activity type. 3) The decision support features of the system provide future labor requirement forecasts on an hourly basis based on past activity. 4) The system includes reports for Daily, Weekly or Monthly reporting of labor usage and wage costs. 5) The system provides an on-line database of all employees. 6) Payroll data can be exported via diskette to a different payroll system. 7) The system can optionally track coupon dropping activities and costs. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM OVERVIEW 2 _________________________________________________________________ LABOR ACTIVITY THEORY The entire system is designed around the different types of labor; ie, Dishwashing, Table Waiting, Driver/Delivery, Kitchen Help, etc. The system calls the different types of labor "ACTIVITIES". Each different activity type has an ACTIVITY CODE and an ACTIVITY DESCRIPTION. Additionally, each activity falls into one of two categories: Direct Labor Cost or Indirect Labor Cost. Direct Labor Costs are costs which are directly related to providing service to a customer; for instance, cooking the meal. Indirect Labor costs are costs which are not directly related to providing service to a customer; for instance, Manager Training. It is important to identify and establish valid activities when originally installing the software because all data is organized around this concept. All reports and history files are directly impacted by any future changes to the activities. Dine-in type restaurant example: Activity Code Activity Description _____________ ____________________ KN Kitchen Help CK Cook / Chef WA Waiter / Waitress DH Dining Room Help TR Training CP Coupon Hanging Carry out / Delivery type restaurant example: Activity Code Activity Description _____________ ____________________ CP Coupon Hanging PH Phone Person OO Operational Time Outside OI Operational Time Inside TR Training Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM OVERVIEW 3 _________________________________________________________________ MILITARY TIME This system uses military time. Military time is based on a 24 hour clock where the following chart explains how military time works. All time fields in the system use military time. Standard Time Military Time Equivalent _____________ ________________________ 1:00 AM 01:00 2:00 AM 02:00 2:30 AM 02:30 . . . . 11:00 AM 11:00 12:00 AM 12:00 1:00 PM 13:00 2:00 PM 14:00 2:30 PM 14:30 3:00 PM 15:00 . . . . 11:00 PM 23:00 11:59 PM 23:59 Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM OVERVIEW 4 _________________________________________________________________ HISTORICAL DATABASES AND DECISION SUPPORT One of the system's strengths is its forecasting functionality. After the system has been in use for one month, its databases will become populated with data required for producing future hourly labor requirements forecast reports. It does this by examining past labor usage and will forecast (via data averaging) what a future day's labor requirements will be. For example: To calculate what next Tuesday's labor requirements are expected to be (by hour, by labor activity type), it will average the last four consecutive Tuesday's data, along with Tuesday from one year ago and forecast this coming Tuesday's requirements. Computerized forecasting of future labor requirements helps the manager to more effectively and accurately schedule future labor requirements. Additionally, new managers can easily master the labor scheduling task. COUPON DROP TRACKING The system can also track the restaurant's coupon issuing history. This functionality can be turned on or off depending on the establishment's requirements. Coupon reports can be generated by date ranges for tracking coupon hanging volumes and costs. Copyright (C) 1989-1991 Restaurant Management Systems GETTING STARTED 5 _________________________________________________________________ SYSTEM INSTALLATION Software installation is divided into the following three steps: 1) Verifying the system hardware requirements are met, 2) Loading the Software onto the machine, 3) Loading the reference tables. SYSTEM REQUIREMENTS 1) IBM compatible AT class machine (286, 386 or greater) 2) Color Monitor, CGA, EGA or VGA. 3) At least 40 meg of available hard drive space for starters. The history files get quite large over time and the forecasting capabilities of the system rely heavily on the history files. 4) Tape Backup System (Optional). 5) One 3.5 or 5.25 diskette drive. 6) 2400 Baud Modem for customer support purposes. 7) The system will operate on any IBM compatible PC running DOS Version 3.3 or greater, or OS/2, V1.3 or greater. The system has not been tested with MicroSoft Windows. The amount of required hard disk space is dependent on the following items: 1) How long the data is kept before being purged from the system. It is recommended to keep data 45 to 60 days on the Daily Time Records File and for 380 days on all other history files. 2) Number of active employees. 3) Number of different types of activities. Copyright (C) 1989-1991 Restaurant Management Systems GETTING STARTED 6 _________________________________________________________________ INSTALLING THE SOFTWARE 1) Make a backup of the original software diskette. Put the original in a safe place and use the backup version from now on. 2) Put diskette in drive A: or drive B: and type: A:INSTALL or B:INSTALL 3) The installation program prompts for the directories on the hard drive where you want to load the software. Hit enter to accept the default directories if you are unsure. 4) After the installation process is complete, reboot the system by hitting the "CTRL ALT DELETE" key sequence. 5) Modify file RMSEBK02.BAT. This file is in the C:\RMS\BIN directory (If you accepted the defaults in step 2). This is the user defined system backup command file. Depending on your hardware configuration, load the correct commands for doing a complete system backup in this file. The default command loaded in this batch file is: BACKUP C:\ A:/S This command will backup the C: drive to the A: drive, all subdirectories. Copyright (C) 1989-1991 Restaurant Management Systems GETTING STARTED 7 _________________________________________________________________ LOADING THE REFERENCE TABLES 1) Load the ACTIVITY CODES table. See function documentation regarding ACTIVITY CODE table maintenance. Additionally, review the section entitled Labor Activity Theory. 2) If coupon tracking will be used, load the COUPON AREA CODES table. See function documentation regarding COUPON AREA CODES table maintenance. 3) Load the EMPLOYEE CLASSES table. See function documentation regarding EMPLOYEE CLASSES table maintenance. 4) Load the EMPLOYEE MASTER table. See function documentation regarding EMPLOYEE MASTER table maintenance. 5) Load the SYSTEM SETUP table. See function documentation regarding SYSTEM SETUP table maintenance. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 8 _________________________________________________________________ LEARNING BROWSE Browse allows the user to easily scan through a database to modify and add records. The user can search for given values and reposition to any record in the database. The switch between the browse and edit screens is a single keystroke. The ordering of the database records can be altered to reflect any index file that has been specified. All levels of users, from the novice to the veteran, will find Browse easy to learn and use. MANUAL CONVENTIONS Some keys or key combinations are represented as one or two words with angle brackets around them. Examples: Key Description ___ ___________ <Esc> Represents the <Esc> key. <Ctrl Home> Represents holding down the <Ctrl> key and pressing the <Home> key. <Shift F1> Represents holding a <Shift> key and pressing the <F1> key. BASIC TERMS AND OPERATIONS Understanding the following terms and operations is essential because they are used throughout Browse. For easiest understanding, read them in the order presented. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 9 _________________________________________________________________ FILE A file is information which is saved on a computer disk. Files have names which identify them. These names are up to eight characters long and are followed by a period and a file name extension of ".DBF" . EMPMASTR.DBF is an example of a file name with the extension ".DBF". DATABASE A database is a special kind of file which stores your data. For example, the Employee Master Database contains the names and addresses of employees. RECORD Database information is organized into records. Each record in the Employee Master database contains information on one person. INDEX FILE It may be necessary to examine a database in different orders at different times. For example, the Employee Master can be sorted by Employee Number or Name. It would take a long time to re-sort a large database every time a new order was required. Consequently, index files are created to permanently contain sorted information. An index file contains one sort order for one database. Because information is already sorted, Browse displays and locates records quickly using index files. WINDOW A window is an area of the screen which is used to display and modify database information. Windows are surrounded by a lined box. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 10 _________________________________________________________________ BROWSE FUNCTION Browse is used for browsing and editing a database, and to select index files for sorting and searching. The screen consists of a menu along the top of the screen, with the majority of the window displaying the database, according to the sorted index. Once the database is displayed, records can be added, modified or marked for deletion. Records can also be located quickly by using index files or by scrolling. CURRENT RECORD The current record is the record at which the cursor is displayed. When several records are displayed in a window, the current record may be changed by pressing the <Up> and <Down> arrow keys. Pressing <Up> moves the cursor to the previous record and pressing <Down> moves the cursor to the next record. MENU A menu is a list of options from which you can select. Press <Enter> when you have the menu option needed. The appropriate arrow keys change the highlighted option. When <Enter> is pressed, the menu's highlighted option is selected. COMMAND ENTRY All Browse commands are initiated by pressing either a single key or a key combination. For example, pressing T or <ALT T> initiates the Top command. All the Browse commands can be initiated by pressing the appropriate letter, or by pressing the letter along with the <ALT> key. Some commands gain access to a menu and others request additional information. Finish the command by selecting a menu option or entering additional information before initiating a new command. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 11 _________________________________________________________________ ESCAPE KEY Pressing the <Esc> key either cancels or aborts an initiated, but not completed, command or menu option. ENTRY AREAS When information is typed in Browse, it is typed into the active entry area. The active entry area is highlighted and contains the cursor. Pressing <Enter> changes the active entry area to the next entry area. When there are no more entry areas on the screen, pressing <Enter> enters the information. Entry Areas are not always associated with a database record. For example, an Entry Area appears after the Find command is initiated. There are several special command keys which facilitate the entering of information into an Entry Area. Command Key Effect <Ins> Flips between Insert Mode and Replace Mode. In Replace Mode, the character typed replaces the character under the cursor; in Insert Mode, the character typed is inserted before the character under the cursor. When in Insert Mode, the cursor is slightly larger. <Del> Deletes the character under the cursor. <Backspace> Deletes the character to the left of the cursor. <Home> Moves the cursor to the first character position in the Entry Area. <End> Moves the cursor to the end of the entered information. <Left> Moves the cursor one position to the left. <Right> Moves the cursor one position to the right. <Ctrl Y> Deletes all the Entry Area characters under and to the right of the cursor. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 12 _________________________________________________________________ The following commands are used when entering information into a group of Entry Areas: Command Key Effect <Enter>, or Move to the next Entry Area. If there is no <Tab> next Entry Area, then the group of Entry Areas are entered. <Shift Tab> Move to the previous Entry Area. <Ctrl Home> Move to the first Entry Area. <Ctrl End> Move to the last Entry Area. <Ctrl W>, or Enter the group of Entry Areas. This is like <Ctrl E> <Enter> when on the last Entry Area <Esc> Abort the changes made in the Entry Areas. The exact effect of aborting will be determined by the particular group of Entry Areas. <Up> Move to the previous Entry Area. <Down> Move to the next Entry Area. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 13 _________________________________________________________________ MENU SELECTIONS Menus are used throughout Browse to choose from a list of available choices. When <Enter> is pressed, the highlighted choice is selected. Two types of menus exist in Browse. The first menu is present when Browse is initiated. For this menu, the following keys may be used to change the highlighted choice: Key Effect <Left> The highlighted choice moves one to the left. <Right> The highlighted choice moves one to the right. All other menus use the following keys to change the highlighted choice: Key Effect <Up> The highlighted choice moves up one. <Down> The highlighted choice moves down one. <Home> The top option becomes the highlighted choice. <End> The bottom option becomes the highlighted choice. <Esc> Aborts the menu. A - Z Pressing a letter or number highlights the next available option in the menu beginning with the character pressed. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 14 _________________________________________________________________ SCROLLING Scrolling allows the user to browse through the database records. All scrolling is done relative to the current record. PAGE DOWN (Press <PgDn>) The Page Down command scrolls down one window of records. If the window contains one record, the next record will be displayed. If the window contains twenty records, the top record of the new window will contain the record after the last record of the old window screen. If all the records fit within the window, the Page Down command will cause the cursor to position itself at the last record. PAGE UP (Press <PgUp>) The Page Up command scrolls up one window of records; it has the opposite effect of the Page Down command. DOWN ARROW (Press <Down>) The Down Arrow command scrolls forward one record. UP ARROW (Press <Up>) The Up Arrow command scrolls backwards one record. TOP (Press T) The Top command scrolls up to the first record. BOTTOM (Press B) The Bottom command scrolls down to the last record. The selected index file affects scrolling as it determines the "first", "next", "previous", and "last" record. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 15 _________________________________________________________________ HELP (Press H) The Help option is one of the menu choices given in the main menu. When Help is selected, a window pops up which gives command keys which can be pressed. Each command key corresponds to an option which could be selected from a menu. Refer to the Browse Quick Reference for a list of the command keys. MODIFY MENU MODIFY RECORD (Press M) The Modify Record command is used to modify the current record. Press <Enter> until the active entry area corresponds to the information to be modified. Then complete the modification by pressing <Ctrl E> or <Ctrl W>. If <Esc> is pressed while modifying a record, the modifications of the entire record are aborted. Pressing another command key using the <Alt> key also completes the modification. In addition, it will initiate the command corresponding to the character entered. DELETE RECORD (Press D) The Delete Record command flags the current record for deletion. An asterisk is displayed by the record to indicate that it is marked for deletion. Note that the records are not actually removed and that a separate program or utility must be used to actually remove the records. UNDELETE RECORD (Press U) The Undelete Record command removes the record deletion mark. This reverses the effect of the Delete Record command. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 16 _________________________________________________________________ ADD BLANK RECORD (Press A) The Add Blank command takes a blank record and appends it to the end of the database file. After executing the command, the entry areas are highlighted. Press <Enter> to move through the entry areas, and when you press the last <Enter> or <Ctrl W>, the record is added and displayed in its proper position in the sorted index. If <Esc> is pressed while adding a record, the Add Blank command aborts and no record is added. Hint : Pressing <ALT A> when adding a record adds the record and starts adding a new record. This is useful when adding several records in a row. ADD COPY RECORD (Press C) The Add Copy command is the same as the Add Blank command except the Add Copy command starts with a copy of the current record. POSITION MENU Record (Press R) The Record command locates a record by its record number. Records are numbered in the order they were added. For example, if there are 5 records in the database, the last record added is record number 5. After initiating the Record command, enter the number of the record to be located. If the record number entered exists, the current record will become the entered record number. The total number of database records will be displayed at the bottom of the screen. If <Esc> is pressed rather than entering a record number, the current record is not changed. If the number entered is negative, or out of range, the current record will not change. If real numbers are entered, the Record number will only look at the whole part of the number, not the fraction (ie. will truncate the remainder). Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 17 _________________________________________________________________ FIND MENU To locate a record quickly, the Find command uses an index file. If the database has several index files, the Select Record Ordering Index command determines which index file is used. The Select Record Ordering Index command also determines the order in which records are displayed. FIND (Press F) The Find command locates a record using an index file. After initiating the Find command, a Find box appears in the middle of the screen. The index being used is given on the first line. A prompt requesting the find information appears on the next line. The information to be entered corresponds to the index file. For example, an index file might order a database according to the name of an individual. In this case, you would enter the name of the person to search for. It is not necessary to enter the complete search information or the completely correct search information. Browse will find the closest match it can. After the Find command is completed, the found record becomes the current record. Example: Entered Find Information -- John Names in the database -- Jackson Kerns Matheson The record with "Kerns" becomes the current record. This is the name after 'John'. Copyright (C) 1989-1991 Restaurant Management Systems USING BROWSE 18 _________________________________________________________________ SELECT RECORD ORDERING INDEX (Press S) The Select Record Ordering Index command accesses a menu containing the index files of the database and the option "Record Number Ordering". Example Menu Contents: 1. Record Number Ordering 2. NAME.NDX In this case, the database only has the index file "NAME.NDX". The menu option corresponding to the current ordering option is initially selected. For example, if "NAME.NDX" was last selected, the next time the menu appears, it will be highlighted. If "Record Number Ordering" is selected, the database will be displayed in the order the records were initially entered. In addition, the first index file on the Select Record Ordering Index menu will be used by the Find commands. If an index file is selected, the database will be displayed in the order determined by the index file. In addition, that index file will be used by the Find command. EDIT/BROWSE SWITCH The Edit/Browse option allows the user to switch between edit mode and browse mode. In the browse mode, the user can look at many records at one time and move freely among them. Note that if all of the record does not fit in the window, only a subset will be displayed. To see more of the records, you must select the Edit option. Under the Edit option, only one record is displayed at a time. The same commands are available with the edit option as with the browse option. EXITING BROWSE The Exit command (Press X) is used to exit Browse. Changes to the contents of the database and index files were made immediately after each record was modified or added. The records marked for deletion will remain marked and continue to exist in the database until the database file is packed. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 19 _________________________________________________________________ MAIN MENU FUNCTION The main menu is the starting point from which the user accesses the system. The main menu branches to all functions which are required for the daily operation of the system. The main menu can be initiated by executing the command EZTIME from the command line or DOS prompt. See the Using Browse section for a description of menus. The main menu displays a horizontal menu across the top of the screen with the following selections: - Update Reference Tables - Post Employee Time Records - Run Dayend Processes - Export Payroll Data - Browse History Files - Print Registration Request Form - Print User Guide - Exit MAIN MENU - Update Reference Tables The Easy Time database is made up of several files (or tables). A file is a collection of records which share the same data elements but have different data values. Reference tables include data which does not change often and they describe the characteristics of your restaurant. Before the system can be used, all reference tables must be established. The TABLES selection displays a pop-up sub-menu for maintenance of all reference tables and includes update capabilities for the following tables: - Activity Codes Reference Table Maintenance - Coupon Area Codes Reference Table Maintenance - Employee Classes Reference Table Maintenance - Employee Master Reference Table Maintenance - System Setup Reference Table Maintenance - Pack Reference Tables Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 20 _________________________________________________________________ MAIN MENU - Post Employee Time Records The RMS Labor Management System processing is based on time records. Each time record represents one shift or block of time an employee has worked. Time records are entered as input to the system; the system processes the data and produces reports as output. Unlike other options on the main menu which bring up a sub-menu, selecting this option executes the function for posting time records. MAIN MENU - Run Dayend Processes At the end of every day, the dayend process must be run. This process calculates the day's labor activity and adds data to the history files for a given day. There is also special weekly and monthly processing which happens automatically if dayend is run every day. The system is designed for dayend to run once per day. If your restaurant is closed on Monday, on Tuesday, dayend must be run for Monday first, then enter Tuesday's time records, then run dayend for Tuesday. If your restaurant is closed two days, then the system day end process must be run once for each of the days you were closed (two in this example). Then enter the first open day's time records and run day end again. There are three options on the dayend sub-menu: - Database Backup - System Backup - Nightly Batch Processes Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 21 _________________________________________________________________ MAIN MENU - Generate Reports This selection displays a pop-up sub-menu for report generation. Before any data is available for reporting purposes, the time records must be entered and the dayend process must be run. - Labor Usage by Activity Code - Coupon Drop Report - Daily Labor Detail Report - Daily Forecast by Activity Code - Daily Forecast by Activity Type MAIN MENU - Export Payroll Data EZTIME is not designed to be a payroll system; there are already many good payroll systems available on the market. However, most general purpose payroll systems don't have the ability to generate reports and forecast future labor requirements the way EZTIME does. This system is designed to be the "front end" of a payroll system for a restaurant. As such, it has the ability to create output data to send to a foreign system as input. This EXPORT selection displays a sub-menu for exporting data to a foreign payroll system. - Export Payroll Data to File - Produce Payroll Report MAIN MENU - Browse History Files The RMS Labor Management System generates several reports with information based on historical data. The historical data is kept on-line until it meets the purge criterion set up in the system setup table. All historical data is available for display. It is also possible to update this data, but updates should only be done with extreme caution, as reports and forecasts are done using the history tables. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 22 _________________________________________________________________ This HISTORY selection displays a pop-up sub-menu for browsing the history tables. - Hourly Labor History - Activity History - Employee Time Records - Coupon Drop History MAIN MENU - Print Registration Request Form This option prompts you for your address, and the number of licenses you wish to purchase. Then it prints an order requisition for you to mail along with your check. MAIN MENU - Print User Guide This option allows you to print the EZTIME User's Guide. MAIN MENU - Exit This selection will exit the EZTIME main menu. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 23 _________________________________________________________________ ACTIVITY CODES TABLE MAINTENANCE This function is used for updating the Activity Code Table. See also Labor Activity Theory in the beginning of this manual. This table is one of the most critical tables in the system because the entire database is built around the concept of different types of labor activities. Careful consideration should be given to the initial implementation of this table in order to provide maximum positive benefit of the system. Future changes (after initial implementation) to this table will probably have a significant impact on operational procedures. Each different type of labor needs an entry in this table. If your restaurant already has the labor categories broken out into types, use the categories that are already established if they are acceptable. If your restaurant does not currently track labor requirements in this manner, think through how you will want to track past labor usage and forecast future labor requirements by activity type. To execute this function: - From the Main Menu, select TABLES. - From the Reference Tables Menu, select ACTIVITY CODES. - See "Using Browse" for updating this table. Fields: CODE This field is a unique two character code which represents a type of labor activity. This field is used extensively throughout the Labor Management System. Activity Code "CP" is reserved for use by the system for "COUPON HANGING". This code turns on special editing functionality in the Post Time Records Function. DESCRIPTION This field is a 30 character description of an activity code. TYPE This field is a 1 character identifier. It identifies whether a given labor activity is considered direct labor (D) or indirect labor (I). Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 24 _________________________________________________________________ Indexes: ACTIVITY.NDX Unique sort by CODE Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 25 _________________________________________________________________ COUPON AREA CODES TABLE MAINTENANCE If your restaurant is not using this functionality, this table has no impact on the system and can safely be disregarded. This function is used for establishing the area codes, sectors or regions where coupons are dropped. Typically, coupons are dropped in sectors within an area which a restaurant serves. This system will track coupon dropping activity by sector. To execute this function: - From the Main Menu, select TABLES. - From the Reference Tables Menu, select COUPON AREA CODES. - See "Using Browse" for updating this table. Fields: CODE Any unique six character code. Each coupon drop area has a unique code associated with it. This field represents an area, region or sector where coupons have been or could be dropped. DESCRIPTION This 30 character field describes an area, region or sector where coupons have been or could be dropped. Each coupon area code has a description associated with it. Indexes: COUPAREA.NDX Unique sort by CODE Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 26 _________________________________________________________________ EMPLOYEE CLASSES TABLE MAINTENANCE This function is used for establishing the different types of employee classes. Classes are user defined types of employees. Each employee in the employee master table is assigned an employee class. To execute this function: - From the Main Menu, select TABLES. - From the Reference Tables Menu, select EMPLOYEE CLASSES. - See "Using Browse" for updating this table. Fields: CODE Any unique two character code. Each employee class must be assigned a unique class code. DESCRIPTION Any 30 byte description. Each type of employee is assigned to an employee class and each class code has a description. Indexes: CLASCODE.NDX Unique sort by CODE Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 27 _________________________________________________________________ EMPLOYEE MASTER TABLE MAINTENANCE This function is used for establishing all the employees in the system. Each employee must be loaded into this table before any time records are posted to the employee. Before this table can be updated, table Employee Classes must be built. Each employee in the employee master table has an employee class assigned. When loading an employee for the first time, put a '0' (numeric zero) in field MINS WKD THIS PD. After that, do not update this field. To execute this function: - From the Main Menu, select TABLES. - From the Reference Tables Menu, select EMPLOYEE MASTER. - See "Using Browse" for updating this table. Fields: NUMBER Each employee must be assigned a unique four character employee number. This field is used for storing the employee's number. NAME This 30 character field is used for storing the employee's name. It is recommended that all employee's names be entered in a consistent manner; ie, "Last ,First" or "First MI. Last". ADDRESS These two 30 character fields are used for storing an employee's address. CITY This field is the employee's city. STATE This field is the employee's home state. POSTAL CODE This field is used for storing the employee's postal number. In the U.S.A., this would be the employee's zip code. PHONE NO This field is used for storing the employee's phone number. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 28 _________________________________________________________________ DRIVERS LIC NO This field is used for storing a drivers license number. STATUS This field is used for storing the employee's status. CLASS Each type of employee is assigned to an employee class. OT CODE This field determines which type of overtime calculations should be performed for the employee. 1 - No overtime pay 2 - Straight Time overtime pay 3 - Time and one half overtime pay If additional overtime pay types are required, contact RMS and request an update to the software to handle your overtime processing requirements. See section 8, System Customization Requests. HOURLY RATE This field is used for storing the employee's hourly wage rate. If the employee is on salary, divide the pay period salary by the number of hours in a pay per period ( $400 / 40 = $10.00 ). MINS WKD THIS PD This field is used internally by the programs which calculate overtime. It should be set to zero when an employee is initially loaded into the system. After that, if the field is modified, it may cause incorrect overtime calculations to be calculated. OVER/UNDER AMT This field may be used for keeping a running total amount of how much an employee may owe the restaurant or vice versa. This is a user field and may be used any way you see fit. It can store a negative or positive amount. USER TEXT 1 These fields may be used for storing any user USER TEXT 2 defined data for an employee. Indexes: EMPMAST1.NDX Unique sort by EMPLOYEE NUMBER EMPMAST2.NDX Not unique sort by EMPLOYEE NAME Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 29 _________________________________________________________________ SYSTEM SETUP TABLE MAINTENANCE This table has only one row in it. If this table has more than one row, the system will use the first not-deleted row it finds starting at the beginning of the file. This table establishes the system configuration at your installation. To execute this function: - From the Main Menu, select TABLES. - From the Reference Tables Menu, select SYSTEM SETUP. - See "Using Browse" for updating this table. Fields: STORE NUMBER If your store is assigned a store number, load the store number in this field. STORE DATE This is an important field in the system. All history data is based on store date. All time records are entered for a store date and associated with a particular store date. Each dayend process is for a store date. When the system is first installed, set store date to the date which you want to start processing for. After that, this field is maintained automatically by the dayend process. LUNCH HOUR START TIME This field stores the time for which lunch hour begins. Typically, this is 1100 for 11 AM. LUNCH HOUR STOP TIME This field stores the time for which lunch hour is over. Typically, this is 1300 for 1 PM. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 30 _________________________________________________________________ LABOR GOAL PERCENT This field is used for storing the labor cost goal of the store. If your labor goal is 33% of total revenue, enter .33 in this field. COUPON PROCESSING USED This field turns coupon processing on or off for your restaurant. If you do not issue coupons, set this to 'N'. If you do issue coupons, set this switch to 'Y'. COUPON UNIT COST This field represents the variable cost for a coupon, excluding labor costs. For example, if it cost $25.00 for 1000 coupons, the per unit coupon cost would be $25 / 1000 = $.025. This amount is used for the calculation of coupon drop costs and is factored into the total amount in the coupon history file. OT PROCESSING USED This field turns overtime processing on or off for your restaurant. If you do not pay overtime, set this to 'N'. If you do, set this switch to 'Y'. HOURS IN OT CALCULATION This field stores the number of hours an employee must work before starting to accrue overtime pay. Many sites may set this at 40, because after 40 hours per week, they start accruing overtime. If you get overtime time pay after 80 hours in 2 weeks, set this field to 80. If you never pay overtime, set this to 9999. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 31 _________________________________________________________________ DAYS IN OT CALCULATION This field stores the number of days in a pay period for overtime processing. Many sites may set this at 7, because after 40 hours per week, they start accruing overtime. If you get overtime time pay after 80 hours in 2 weeks, set this field to 14. If you never pay overtime, set to 7. OT PAY PERIOD BEGIN DATE This field stores the pay period begin date. It must be entered at system initialization time. After system initialization, it is automatically updated by the dayend batch processes. OT PAY PERIOD END DATE This field stores the pay period end date. It must be entered at system initialization time. After system initialization, it is automatically updated by the dayend batch processes. COUPON HISTORY PURGE DAYS The number of days to maintain data on the Coupon History File. RMS recommends at least 375. ACTIVITY SUMMARY PURGE DAYS The number of days to store data on the Activity Summary History File. RMS recommends at least 375. HOURLY LABOR HISTORY PURGE DAYS The number of days to store data on the Hourly Labor History File. RMS recommends at least 375. TIME RECORD HISTORY PURGE DAYS The number of days to store data on the Time Record History file. RMS recommends from 45 to 60. Indexes: None Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 32 _________________________________________________________________ PACK REFERENCE TABLES This function is used for packing and re-indexing all reference tables. Any records flagged for deletion will be removed and all reference table indexes are rebuilt. To execute this function: - From the Main Menu, select TABLES. - From the Reference Tables Menu, select Pack Reference Tables. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 33 _________________________________________________________________ POST DAILY TIME RECORDS This function is used for entering daily time transactions. Each transaction belongs to one employee. An employee may have one or more transactions entered per day. Each transaction also has a clock in date and time, a clock out date and time, and an activity code. This function has the following edits: 1) The employee number must be found in the employee master table. 2) Clock in date must be a valid date. It must be the same day or one day greater than STORE_DATE. If transactions for previous days need to be entered, see the section on re-running dayend. 3) Clock in time can be any valid military time. 4) Clock Out Date must be a valid date. Additionally, it must be the same as, or one day greater than clock in date. 5) Clock Out time must be a valid military time. Additionally, Clock out date and time must be greater than clock in date and time. 6) Activity Code must be entered and it must be found in the activity Codes Table. Additionally, if Activity Code is 'CP' for coupon hanging, the coupon fields, AREA CODE and NO HUNG, become required. To execute this function: - From the Main Menu, select TIME RECS - See "Using Browse" for updating this table. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 34 _________________________________________________________________ Fields: EMPLOYEE NUMBER This is the employee's number. Each employee must first be entered in the Employee Master Table before data records can be posted for this employee. IN DATE A valid date. Upon original entry of this field, it must be the same or one day greater than STORE_DATE. Each time record has a clock in date which represents the day the employee started to work on a given shift. IN TIME A valid military time. Each time record has a clock in time which represents the time the employee clocked in on a given shift. OUT DATE A valid date. Upon original entry of this field, it must be the same or one day greater than CLK_IN_DAT. Each time record has a clock out date which represents the day the employee clocked out on a given shift. Since it is possible to start work on one day ( before midnight ) and finish work on a different day ( after midnight ), this field may be the same, or one day greater than clock in date. OUT TIME A valid military time. Clock Out Time and Clock Out Date must be greater than Clock In Time and Clock In Date. Each time record has a clock out time which represents the time the employee clocked out on a given shift. ACTIVITY CODE This field is a two character code which represents a type of labor activity. This field is relied upon heavily in the Labor Management Module. All Activity Codes must first be set up in the Activity Codes Table. COUPON AREA This field represents an area, region or sector where coupons have been or could be dropped. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 35 _________________________________________________________________ COUPON NO HUNG This field represents the number of coupons which were hung for a given area. Indexes: EMPTIME.NDX Unique sort by STORE_DATE+EMP_NO+CLK_IN_DAT+CLK_IN_TIM Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 36 _________________________________________________________________ DAYEND DATABASE BACKUP The Database Backup Function backs up the databases into a backup directory. This should be performed at the end of every business day, before you power down the system. The DOS commands to perform a backup can be found in the batch file RMSEBK01.BAT. The default directory for this process is C:\RMS\DATABASE\BACKUP. If you start running out of hard disk space, you can 1) get a bigger hard drive, or, 2) modify this batch file to backup your databases to a different drive, device or directory. RECOVER A PREVIOUS DAYS BACKUP 1) Rename all databases and indexes in the database directory. The default directory for the databases is C:\RMS\DATABASE. C>CD\RMS\DATABASE C>REN *.DAT *.DA1 C>REN *.NDX *.ND1 C>REN *.DBT *.DB1 2) Copy all files from the backup directory to the database directory: C>COPY C:\RMS\DATABASE\BACKUP\*.* C:\RMS\DATABASE\*.* /V 3) After the problems have been resolved, delete the databases which were renamed in step 1. C>DEL *.DA1 C>DEL *.ND1 C>DEL *.DB1 Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 37 _________________________________________________________________ BACKUP PROCESS MODIFICATIONS It is possible to modify this backup process to more closely meet your backup needs. The installed configuration only backs up the last day. Some sites may want to keep more than one day's backup. To modify the process, simply put the required operating system commands in file RMSEBK01.BAT. SYSTEM BACKUP This is a user defined function which must be customized for each site. Because of the many different hardware configurations this software may run on, it is not practical to build this function as it would probably be modified on site. The important point here is, BACKUP YOUR SYSTEM on a regular basis. NIGHTLY BATCH PROCESS After all the time records for the day have been posted using the Post Daily Time Records function, the nightly batch process must be run. This function processes all the time records for the day. It calculates labor costs on an hourly and daily basis. It updates all the history tables with today's data and, finally, it moves all of today's time records into the time record history file. Dayend removes time records flagged for deletion and does not use them for its data update processes. This process must be run once per day, even if the restaurant is not open for a given day. If you need to skip a day, run this process once for each day skipped without entering any time transactions. To see which day the system is processing for, look in the STORE table using the SYSTEM SETUP function and examine field STORE DATE. The risk of not running this process daily is that overtime calculation processing will not calculate amounts correctly. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 38 _________________________________________________________________ REPORTS Before time records are available for reporting purposes, all transactions must be entered via the Post Daily Time Records Function and the daily batch process must have been run. The daily batch process performs several calculations against the time records before posting the data into the history tables. The reports are generated using the history tables for input. These report functions generally prompt for desired parameters before generating the report. They typically require an input date, or input date range. Some of the reports also prompt for a condensed or expanded format. The condensed format typically prints summary information while the expanded formats print detail and summary information. Samples of these reports can be found in the appendix of this manual. LABOR USAGE BY ACTIVITY CODE This report can be used for determining daily, weekly or monthly labor utilization and costs. It breaks the labor resources used and costs out by activity code. The function prompts for a date range. COUPON DROP REPORT This report prints coupon drop information by area code and date. DAILY LABOR DETAIL REPORT This report is a detail listing of the time records posted for a given day. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 39 _________________________________________________________________ DAILY LABOR FORECAST BY ACTIVITY CODE This report lists hourly historical activity by activity code for the last four weeks plus one year ago. Based on this information, the data is averaged and a system generated forecast is presented for a given activity code. This forecasting method works when there are not dramatic fluctuations in the business. For example, if on Mothers Day, the restaurant is five times busier than normal, you should disregard the system generated forecast and plan accordingly. If there is at least one year's data in the system, look at last year's requirements for a more accurate requirement for this year. DAILY LABOR FORECAST BY ACTIVITY TYPE This report is the same as report Daily Labor Forecast by Activity Code except the break out is by activity type, rather than activity code. Activity types are direct labor costs and indirect labor costs. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 40 _________________________________________________________________ EXPORT PAYROLL DATA TO FILE This function generates a file on disk which can be used as input to a foreign payroll system. The menu prompts for a date range of transactions and requests a file name for output of the records. A suggested procedure is to generate the diskette on a regular basis for input to your payroll system. Label the diskette as time transactions from MMM/DD/YY to MMM/DD/YY. Keep these diskettes for as long as you want to keep a history of daily time transactions. The default file name is A:RMSPYROL.OUT The format of the transactions is: Employee Number Char 9 Space Char 1 Store Date YYYYMMDD Space Char 1 Clock In Date YYYYMMDD Clock In Time HHMM Space Char 1 Clock Out Date YYYYMMDD Clock Out Time HHMM Space Char 1 Standard Hours Worked Numeric 6.2 OT Hours Worked Numeric 6.2 Total Hours Worked Numeric 6.2 Space Char 1 Standard Pay Numeric 7.2 OT Pay Numeric 7.2 Total Pay Numeric 7.2 PRODUCE PAYROLL REPORT This function produces a hard copy of the data which was just loaded onto the diskette. This function should be executed after the export function is executed. The date range is entered in the export function and "remembered". This function produces a report based on the date range entered in the previous function. Copyright (C) 1989-1991 Restaurant Management Systems SYSTEM FUNCTIONS 41 _________________________________________________________________ BROWSE HISTORY TABLES These functions are intended for browsing only. The history tables are automatically updated by dayend processing and the files are "locked" after dayend is done. Updating to these files by any user function or custom modification may be dangerous and produce inaccurate data in these files. Inaccurate data in these files may lead to inaccurate reports which in turn may lead to business decisions made on inaccurate data. HOURLY LABOR HISTORY This table maintains an hourly breakdown by activity of resources used and hourly costs. ACTIVITY HISTORY This table maintains summary level data by activity by date. EMPLOYEE TIME RECORDS This table is a copy of all employee time records. COUPON DROP HISTORY This table maintains coupon drop information. Copyright (C) 1989-1991 Restaurant Management Systems ERROR MESSAGES 42 _________________________________________________________________ ADHOC REPORTING REQUIREMENTS Closed systems are generally a hindrance to those who try to use it. Of primary concern to the developer of this system was in keeping the system "open" to the user community. The EZTIME system was designed using the "relational" model and was implemented on the industry standard DBASE IV file structure. Eventually, you will need reports which were not supplied, or you will need to "query" the system with a specific question, and try to get a specific answer based on the data in the files. There are many high quality tools on the market which will allow you to do these types of things with DBASE IV files. The system as it is supplied provides a working design, a documented set of files and fields (see data dictionary), data collection forms and a complete menu structure. The current release of this system, however, does not supply a user "Adhoc Reporting" feature at this time. For up to several hundred dollars, you can purchase a tool set (DBASE IV, Object Vision, Q&E Database Editor ) which will provide a mechanism for Adhoc reporting requirements. SYSTEM MODIFICATION WARNING With open systems, comes the possibility of system modifications. Custom reporting can safely be assumed, as reports only read the files. If the application is being modified and the databases are being updated by modified programs, be sure you have an understanding of the functionality of the system before proceeding with modifications. Be especially wary of modifications to the system by anyone who is not familiar with the way the application functions. SYSTEM MODIFICATIONS REQUESTS RMS provides modification and consulting services for this software system. Current rates are $50.00 per hour. Contact RMS if you need the system modified. Example modifications include special reporting requirements, or special time code calculations. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 43 _________________________________________________________________ TABLES Each table has its own file name. All tables or databases end with the file extension of .DBF . Each file has zero, one or two index files associated with it. The indexes may or may not be unique. Table Description File Name Indexes File Type _________________ _________ _______ _________ Activity Codes ACTIVITY.DBF ACTIVITY.NDX Reference Activity Summary History ACTSUM.DBF ACTSUM1.NDX History ACTSUM2.NDX Coupon Area Codes COUPAREA.DBF COUPAREA.NDX Reference Coupon Summary History CUPONHST.DBF CUPONHST.NDX History Employee Classes CLASCODE.DBF CLASCODE.NDX Reference Employee Master EMPMASTR.DBF EMPMAST1.NDX Reference EMPMAST2.NDX Hourly Labor History LABORHST.DBF LABORHST.NDX History Overtime Codes OT_CODES.DBF OT_CODES.NDX Reference System Setup STORE.DBF none Reference Time Records EMPTIME.DBF EMPTIME.NDX Operational Time Records History EMPTIMEH.DBF EMPTIMEH.NDX History INDEXES INDEX UNIQUE SORT ORDER _____ ______ __________ ACTIVITY YES ACT_CODE ACTSUM1 YES STORE_DATE + ACT_CODE ACTSUM2 YES ACT_CODE + STORE_DATE CLASCODE YES CLAS_CODE COUPAREA YES CPN_AREACD CUPONHST YES STORE_DATE + CPN_AREACD EMPMAST1 YES EMP_NO EMPMAST2 NO EMP_NAME EMPTIME YES STORE_DATE + EMP_NO + CLK_IN_DAT + CLK_IN_TIM EMPTIMEH NO STORE_DATE + ACT_CODE + CLK_IN_DAT + CLK_IN_TIM LABORHST YES STORE_DATE + ACT_CODE OTCODES YES OT_CODE Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 44 _________________________________________________________________ FIELD LISTING BY TABLE TABLE: ACTIVITY CODES (ACTIVITY.DBF) FIELDS: ACT_CODE, ACT_DESC, ACT_TYPE TABLE: ACTIVITY SUMMARY HISTORY (ACTSUM.DBF) FIELDS: STORE_DATE, ACT_CODE ST_HRS, OT_HRS, LH_HRS, TOT_HRS ST_PAY, OT_PAY, LH_PAY, TOT_PAY TABLE: COUPON AREA CODES (COUPAREA.DBF) FIELDS: CPN_AREACD, CPN_AREADS TABLE: COUPON SUMMARY HISTORY (CUPONHST.DBF) FIELDS: STORE_DATE, CPN_AREACD, CPNS_HUNG, CPN_COST TABLE: EMPLOYEE CLASSES (CLASCODE.DBF) FIELDS: CLAS_CODE, CLAS_DESC TABLE: EMPLOYEE MASTER (EMPMASTR.DBF) FIELDS: EMP_NO, EMP_NAME, EMP_ADDRS1, EMP_ADDRS2 EMP_CITY, EMP_STATE, EMP_PSTCOD, EMP_PHONE EMP_WAGE, CLAS_CODE, DRV_LIC_NO, EMP_STS OV_UN_AMT, OT_CD, PP_MINS_TD USER_TEXT1, USER_TEXT2 DEF_ACT_CD *reserved for next release Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 45 _________________________________________________________________ TABLE: HOURLY LABOR HISTORY (LABORHST.DBF) FIELDS: STORE_DATE, ACT_CODE, HRS_WKD_1, HRS_WKD_2, HRS_WKD_3, HRS_WKD_4 HRS_WKD_5, HRS_WKD_6, HRS_WKD_7, HRS_WKD_8 HRS_WKD_9, HRS_WKD_10, HRS_WKD_11, HRS_WKD_12 HRS_WKD_13, HRS_WKD_14, HRS_WKD_15, HRS_WKD_16 HRS_WKD_17, HRS_WKD_18, HRS_WKD_19, HRS_WKD_20 HRS_WKD_21, HRS_WKD_22, HRS_WKD_23, HRS_WKD_24 HRS_WKD_25, HRS_WKD_26, HRS_WKD_27, HRS_WKD_28 HRS_WKD_29, HRS_WKD_30 LAB_CST_1, LAB_CST_2, LAB_CST_3, LAB_CST_4 LAB_CST_5, LAB_CST_6, LAB_CST_7, LAB_CST_8 LAB_CST_9, LAB_CST_10, LAB_CST_11, LAB_CST_12 LAB_CST_13, LAB_CST_14, LAB_CST_15, LAB_CST_16 LAB_CST_17, LAB_CST_18, LAB_CST_19, LAB_CST_20 LAB_CST_21, LAB_CST_22, LAB_CST_23, LAB_CST_24 LAB_CST_25, LAB_CST_26, LAB_CST_27, LAB_CST_28 LAB_CST_29, LAB_CST_30 TABLE: OVERTIME CODES (OTCODES.DBF) FIELDS: OT_CD, OT_DESC TABLE: SYSTEM SETUP (STORE.DBF) FIELDS: STORE_NO, LH_ST_TIME, LH_SP_TIME, STORE_DATE CPNUNITCST, PRINTERID1, LABOR_GOAL, OT_HRS_CLC OT_DYS_RST, OT_PP_BDAT, OT_PP_EDAT, OT_SWITCH CP_SWITCH, PE_ST_DT, PE_SP_DT, RMS_PRG_1 RMS_PRG_2, RMS_PRG_3, RMS_PRG_4, RMS_PRG_5 TABLE: TIME RECORDS, TIME RECORD HISTORY (EMPTIME.DBF, EMPTIMEH.DBF) FIELDS: EMP_NO, STORE_DATE, CLK_IN_DAT, CLK_IN_TIM CLK_OT_DAT, CLK_OT_TIM, ST_MINS_WK, OT_MINS_WK LH_MINS_WK, STD_PAY, OT_PAY, LH_PAY ACT_CODE, CPN_AREACD, CPNS_HUNG, PROCESS_1 PROCESS_2, PROCESS_3, PROCESS_4, PROCESS_5 Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 46 _________________________________________________________________ FIELD NAME: ACT_CODE FIELD NAME: FIELD DESCRIPTION: ACTIVITY CODE FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 2 LENGTH: ALLOWABLE VALUES: Any text data. Each code most be unique. ALLOWABLE VALUES: ASSOCIATED TABLES: ACTIVITY, ACTSUM, EMPTIME, EMPTIMEH, LABORHST ASSOCIATED TABLES: ASSOCIATED INDEXES: ACTIVITY, ACTSUM1, ACTSUM2, EMPTIMEH, ASSOCIATED INDEXES: LABORHST DESCRIPTION: This field is a two character code which DESCRIPTION: represents a type of labor activity. This field is relied upon heavily in the Labor Management Module. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 47 _________________________________________________________________ FIELD NAME: ACT_DESC FIELD NAME: FIELD DESCRIPTION: ACTIVITY DESCRIPTION FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 30 LENGTH: ALLOWABLE VALUES: Any 30 character description. ALLOWABLE VALUES: ASSOCIATED TABLES: ACTIVITY ASSOCIATED TABLES: ASSOCIATED INDEXES: ACTIVITY ASSOCIATED INDEXES: DESCRIPTION: This field is a 30 character description of a DESCRIPTION: given activity code. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 48 _________________________________________________________________ FIELD NAME: ACT_TYPE FIELD NAME: FIELD DESCRIPTION: ACTIVITY TYPE FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 1 LENGTH: ALLOWABLE VALUES: I, D ALLOWABLE VALUES: ASSOCIATED TABLES: ACTIVITY ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is a 1 character identifier. It DESCRIPTION: identifies whether a given labor activity is considered direct labor (D) or indirect labor (I). Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 49 _________________________________________________________________ FIELD NAME: CLAS_CODE FIELD NAME: FIELD DESCRIPTION: Employee Class Code FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 2 LENGTH: ALLOWABLE VALUES: Any two byte character string. Each employee ALLOWABLE VALUES: class must be assigned a unique class code. ASSOCIATED TABLES: CLASCODE, EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: CLASCODE ASSOCIATED INDEXES: DESCRIPTION: Each type of employee is assigned to an DESCRIPTION: employee class. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 50 _________________________________________________________________ FIELD NAME: CLAS_DESC FIELD NAME: FIELD DESCRIPTION: Employee Class Description FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 30 LENGTH: ALLOWABLE VALUES: Any 30 byte description. ALLOWABLE VALUES: ASSOCIATED TABLES: CLASCODE ASSOCIATED TABLES: ASSOCIATED INDEXES: CLASCODE ASSOCIATED INDEXES: DESCRIPTION: Each type of employee is assigned to an DESCRIPTION: employee class and each class code has a description. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 51 _________________________________________________________________ FIELD NAME: CLK_IN_DAT FIELD NAME: FIELD DESCRIPTION: Clock In Date FIELD DESCRIPTION: EDIT TYPE: DATE EDIT TYPE: LENGTH: 8 LENGTH: ALLOWABLE VALUES: A valid date. Upon original entry of this ALLOWABLE VALUES: field, it must be the same or one day greater than STORE_DATE. ASSOCIATED TABLES: EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: EMPTIME, EMPTIMEH ASSOCIATED INDEXES: DESCRIPTION: Each time record has a clock in date which DESCRIPTION: represents the day the employee started to work on a given shift. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 52 _________________________________________________________________ FIELD NAME: CLK_IN_TIM FIELD NAME: FIELD DESCRIPTION: Clock In Time FIELD DESCRIPTION: EDIT TYPE: TIME EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: A valid military time. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: EMPTIME, EMPTIMEH ASSOCIATED INDEXES: DESCRIPTION: Each time record has a clock in time which DESCRIPTION: represents the time the employee clocked in on a given shift. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 53 _________________________________________________________________ FIELD NAME: CLK_OT_DAT FIELD NAME: FIELD DESCRIPTION: Clock Out Date FIELD DESCRIPTION: EDIT TYPE: DATE EDIT TYPE: LENGTH: 8 LENGTH: ALLOWABLE VALUES: A valid date. Upon original entry of this ALLOWABLE VALUES: field, it must be the same or one day greater than CLK_IN_DAT. ASSOCIATED TABLES: EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: Each time record has a clock out date which DESCRIPTION: represents the day the employee clocked out on a given shift. Since it is possible to start work on one day ( before midnight ) and finish work on a different day ( after midnight ), this field may be the same, or one day greater than clock in date. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 54 _________________________________________________________________ FIELD NAME: CLK_OT_TIM FIELD NAME: FIELD DESCRIPTION: Clock Out Time FIELD DESCRIPTION: EDIT TYPE: TIME EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: A valid military time. Clock Out Time and ALLOWABLE VALUES: Clock Out Date must be greater than Clock In Time and Clock In Date. ASSOCIATED TABLES: EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: Each time record has a clock out time which DESCRIPTION: represents the time the employee clocked out on a given shift. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 55 _________________________________________________________________ FIELD NAME: CPN_AREACD FIELD NAME: FIELD DESCRIPTION: Coupon Area Code FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 6 LENGTH: ALLOWABLE VALUES: Any six character code. Each coupon drop ALLOWABLE VALUES: area has a unique code associated with it. ASSOCIATED TABLES: COUPAREA, CUPONHST, EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: COUPAREA, CUPONHST ASSOCIATED INDEXES: DESCRIPTION: This field represents an area, region or DESCRIPTION: sector where coupons have been or could be dropped. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 56 _________________________________________________________________ FIELD NAME: CPN_AREADS FIELD NAME: FIELD DESCRIPTION: Coupon Area Code Description FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 30 LENGTH: ALLOWABLE VALUES: Any 30 character description. ALLOWABLE VALUES: ASSOCIATED TABLES: COUPAREA, CUPONHST, EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: COUPAREA, CUPONHST ASSOCIATED INDEXES: DESCRIPTION: This field describes an area, region or DESCRIPTION: sector where coupons have been or could be dropped. Each coupon area code has a description associated with it. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 57 _________________________________________________________________ FIELD NAME: CPN_COST FIELD NAME: FIELD DESCRIPTION: Coupon Drop Cost FIELD DESCRIPTION: EDIT TYPE: MONEY EDIT TYPE: LENGTH: 6.2 LENGTH: ALLOWABLE VALUES: Display only field, calculated field. ALLOWABLE VALUES: ASSOCIATED TABLES: CUPONHST ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field represents the cost for a coupon DESCRIPTION: drop, for a given day, for a given area code. It is a calculated field and includes both labor costs and coupon unit costs. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 58 _________________________________________________________________ FIELD NAME: CPNS_HUNG FIELD NAME: FIELD DESCRIPTION: Coupons Hung FIELD DESCRIPTION: EDIT TYPE: INTEGER EDIT TYPE: LENGTH: 6 LENGTH: ALLOWABLE VALUES: 1 to 99999 ALLOWABLE VALUES: ASSOCIATED TABLES: CUPONHST, EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field represents the number of coupons DESCRIPTION: which were hung for a given area. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 59 _________________________________________________________________ FIELD NAME: CPNUNITCST FIELD NAME: FIELD DESCRIPTION: Coupon Unit Cost FIELD DESCRIPTION: EDIT TYPE: MONEY EDIT TYPE: LENGTH: 8.4 LENGTH: ALLOWABLE VALUES: 1 to 999.9999 ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field represents the variable cost for a DESCRIPTION: coupon excluding labor costs. For example, if it cost $25.00 for 1000 coupons, the per unit coupon cost would be $25 / 1000 = $.025. This amount is used for the calculation of coupon drop costs and is factored into the total amount in the coupon history file. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 60 _________________________________________________________________ FIELD NAME: CPN_SWITCH FIELD NAME: FIELD DESCRIPTION: Coupon Processing Switch FIELD DESCRIPTION: EDIT TYPE: LOGICAL EDIT TYPE: LENGTH: 1 LENGTH: ALLOWABLE VALUES: Y, N (yes, no) ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field turns coupon processing on or off DESCRIPTION: for your restaurant. If you do not issue coupons, set this to 'N'. If you do issue coupons, set this switch to 'Y'. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 61 _________________________________________________________________ FIELD NAME: DRV_LIC_NO FIELD NAME: FIELD DESCRIPTION: Driver's License Number FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 15 LENGTH: ALLOWABLE VALUES: Any valid characters. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing a drivers DESCRIPTION: license number. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 62 _________________________________________________________________ FIELD NAME: EMP_ADDRS1, EMP_ADDRS2 FIELD NAME: FIELD DESCRIPTION: Employee Address Line 1 and 2 FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 30 LENGTH: ALLOWABLE VALUES: Any valid characters. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing an employee's DESCRIPTION: address. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 63 _________________________________________________________________ FIELD NAME: EMP_CITY FIELD NAME: FIELD DESCRIPTION: Employee City FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 15 LENGTH: ALLOWABLE VALUES: Any valid characters. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing the city where DESCRIPTION: an employee lives. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 64 _________________________________________________________________ FIELD NAME: EMP_NAME FIELD NAME: FIELD DESCRIPTION: Employee Name FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 30 LENGTH: ALLOWABLE VALUES: Any valid character data. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: EMPMAST2 ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing the employee's DESCRIPTION: name. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 65 _________________________________________________________________ FIELD NAME: EMP_NO FIELD NAME: FIELD DESCRIPTION: Employee Number FIELD DESCRIPTION: EDIT TYPE: INTEGER EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: 1 through 9999 ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR, EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: EMPMAST1, EMPTIME ASSOCIATED INDEXES: DESCRIPTION: Each employee must be assigned a unique DESCRIPTION: employee number. This field is used for storing the employee's number. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 66 _________________________________________________________________ FIELD NAME: EMP_PHONE FIELD NAME: FIELD DESCRIPTION: Employee Phone Number FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 20 LENGTH: ALLOWABLE VALUES: Any phone number. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing the employee's DESCRIPTION: phone number. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 67 _________________________________________________________________ FIELD NAME: EMP_PSTCOD FIELD NAME: FIELD DESCRIPTION: Employee Postal Code FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 15 LENGTH: ALLOWABLE VALUES: Any character data. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing the employee's DESCRIPTION: postal number. In the U.S.A., this would be the employee's zip code. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 68 _________________________________________________________________ FIELD NAME: EMP_STATE FIELD NAME: FIELD DESCRIPTION: Employee State FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 2 LENGTH: ALLOWABLE VALUES: Any character data. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing the employee's DESCRIPTION: home state. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 69 _________________________________________________________________ FIELD NAME: EMP_STS FIELD NAME: FIELD DESCRIPTION: Employee Status FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 1 LENGTH: ALLOWABLE VALUES: A, L, T ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing the employee's DESCRIPTION: status. A = Active Employee L = On Leave (Employee taking leave of absence) T = Terminated (Employee has terminated employment) Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 70 _________________________________________________________________ FIELD NAME: EMP_WAGE FIELD NAME: FIELD DESCRIPTION: Employee Wage FIELD DESCRIPTION: EDIT TYPE: MONEY EDIT TYPE: LENGTH: 5.2 LENGTH: ALLOWABLE VALUES: A valid hourly rate. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing the employee's DESCRIPTION: hourly wage rate. If the employee is on salary, divide the pay period salary by the number of hours in a pay period. $400 / 40 = $10.00. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 71 _________________________________________________________________ FIELD NAME: LAB_CST_1 through 30 FIELD NAME: FIELD DESCRIPTION: Labor Cost 1 - 30 FIELD DESCRIPTION: EDIT TYPE: Money EDIT TYPE: LENGTH: 7.2 LENGTH: ALLOWABLE VALUES: Display only, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: LABORHST ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: These fields are used for storing the cost of DESCRIPTION: manpower required to run the store for a given hour for a given activity code. For example, if field Labor-Cost-12 is 87.50, that means that wages were $87.50 during the business hours between 11 AM and 12 Noon. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 72 _________________________________________________________________ FIELD NAME: HRS_WKD_1 through 30 FIELD NAME: FIELD DESCRIPTION: Hours Worked 1 - 30 FIELD DESCRIPTION: EDIT TYPE: Numeric EDIT TYPE: LENGTH: 6.2 LENGTH: ALLOWABLE VALUES: Display only, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: LABORHST ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: These fields are used for storing the amount DESCRIPTION: of manpower required to run the store for a given hour for a given activity code. For example, if field Hours-Worked-12 is 8.5, that means that eight and one-half man hours were used in operating the store ( for a given activity ) during the business hours between 11 AM and 12 Noon. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 73 _________________________________________________________________ FIELD NAME: LABOR_GOAL FIELD NAME: FIELD DESCRIPTION: Labor Goal FIELD DESCRIPTION: EDIT TYPE: Percentage EDIT TYPE: LENGTH: 7.4 LENGTH: ALLOWABLE VALUES: A numeric value, less than 100%. ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field is used for storing the labor cost DESCRIPTION: goal of the store. If your labor goal is 33% of total revenue, enter 33.0000 in this field. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 74 _________________________________________________________________ FIELD NAME: LH_HRS FIELD NAME: FIELD DESCRIPTION: Lunch Hour Hours Worked FIELD DESCRIPTION: EDIT TYPE: Numeric EDIT TYPE: LENGTH: 7.2 LENGTH: ALLOWABLE VALUES: Display only field, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: ACTSUM ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the total man hours DESCRIPTION: required to operate the store during the lunch hour rush. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 75 _________________________________________________________________ FIELD NAME: LH_MINS_WK FIELD NAME: FIELD DESCRIPTION: Lunch Hour Minutes Worked FIELD DESCRIPTION: EDIT TYPE: Numeric EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: Display only field, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: These are internally used fields which DESCRIPTION: represent the number of minutes a given time record was active during the lunch hour rush. These fields are ultimately used for calculating the total lunch hour labor requirements which are maintained in the ACTSUM file. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 76 _________________________________________________________________ FIELD NAME: LH_PAY FIELD NAME: FIELD DESCRIPTION: Lunch Hour Pay FIELD DESCRIPTION: EDIT TYPE: Money EDIT TYPE: LENGTH: 6.2 LENGTH: ALLOWABLE VALUES: Display only field, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: ACTSUM, EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the labor costs for lunch DESCRIPTION: hour labor requirements. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 77 _________________________________________________________________ FIELD NAME: LH_SP_TIME FIELD NAME: FIELD DESCRIPTION: Lunch Hour Stop Time FIELD DESCRIPTION: EDIT TYPE: TIME EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: Any valid military time ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the time at which lunch DESCRIPTION: hour is over. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 78 _________________________________________________________________ FIELD NAME: LH_ST_TIME FIELD NAME: FIELD DESCRIPTION: Lunch Hour Start Time FIELD DESCRIPTION: EDIT TYPE: TIME EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: Any valid military time ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the time at which lunch DESCRIPTION: hour begins. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 79 _________________________________________________________________ FIELD NAME: OT_CD FIELD NAME: FIELD DESCRIPTION: Overtime Code FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 1 LENGTH: ALLOWABLE VALUES: 1, 2, 3 ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR, OTCODES ASSOCIATED TABLES: ASSOCIATED INDEXES: OTCODES ASSOCIATED INDEXES: DESCRIPTION: This field stores the type of overtime DESCRIPTION: calculations an employee should have performed on his / her time records. 1 - No O.T. Pay 2 - Straight Time O.T. Pay 3 - Time and One Half O.T. Pay Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 80 _________________________________________________________________ FIELD NAME: OT_DESC FIELD NAME: FIELD DESCRIPTION: Overtime Code Description FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 30 LENGTH: ALLOWABLE VALUES: Predefined descriptions for predefined ALLOWABLE VALUES: overtime codes. ASSOCIATED TABLES: OTCODES ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the description which is DESCRIPTION: associated with a given overtime code. All overtime codes are predefined. If you have special overtime calculation requirements, contact your software vendor. Special overtime codes can be developed for your site fee. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 81 _________________________________________________________________ FIELD NAME: OT_DYS_RST FIELD NAME: FIELD DESCRIPTION: Days in O.T. Calculation FIELD DESCRIPTION: EDIT TYPE: INTEGER EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: Any valid integer ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the number of days in a pay DESCRIPTION: period for overtime processing. Many sites may set this at 7, because after 40 hours per week, they start accruing overtime. If you get overtime time pay after 80 hours in 2 weeks, set this field to 14. If you never pay overtime, set this to 7. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 82 _________________________________________________________________ FIELD NAME: OT_HRS FIELD NAME: FIELD DESCRIPTION: Overtime Hours FIELD DESCRIPTION: EDIT TYPE: Numeric EDIT TYPE: LENGTH: 7.2 LENGTH: ALLOWABLE VALUES: Display only, calculated amount ALLOWABLE VALUES: ASSOCIATED TABLES: ACTSUM ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the total number of DESCRIPTION: overtime hours that were worked on a given date on a given activity. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 83 _________________________________________________________________ FIELD NAME: OT_HRS_CLC FIELD NAME: FIELD DESCRIPTION: Hours In O.T. Calculation FIELD DESCRIPTION: EDIT TYPE: INTEGER EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: Any valid integer ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the number of hours an DESCRIPTION: employee must work before starting to accrue overtime pay. Many sites may set this at 40, because after 40 hours per week, they start accruing overtime. If you get overtime time pay after 80 hours in 2 weeks, set this field to 80. If you never pay overtime, set this field to 9999. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 84 _________________________________________________________________ FIELD NAME: OT_MINS_WK FIELD NAME: FIELD DESCRIPTION: Overtime Minutes Worked FIELD DESCRIPTION: EDIT TYPE: INTEGER EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: Display only, calculated field ALLOWABLE VALUES: ASSOCIATED TABLES: EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the number of minutes a DESCRIPTION: particular time record has overtime associated with it. It is primarily used for rolling up into summation records by later processes and reports. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 85 _________________________________________________________________ FIELD NAME: OT_PAY FIELD NAME: FIELD DESCRIPTION: Overtime Pay FIELD DESCRIPTION: EDIT TYPE: MONEY EDIT TYPE: LENGTH: 6.2 LENGTH: ALLOWABLE VALUES: Display only, calculated field ALLOWABLE VALUES: ASSOCIATED TABLES: ACTSUM, EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the amount of overtime pay. DESCRIPTION: Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 86 _________________________________________________________________ FIELD NAME: OT_PP_BDAT FIELD NAME: FIELD DESCRIPTION: Overtime Pay Period Begin Date FIELD DESCRIPTION: EDIT TYPE: DATE EDIT TYPE: LENGTH: 8 LENGTH: ALLOWABLE VALUES: Any valid date ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the pay period begin date. DESCRIPTION: It must be entered at system initialization time. After system initialization, it is automatically updated by the day end batch processes. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 87 _________________________________________________________________ FIELD NAME: OT_PP_EDAT FIELD NAME: FIELD DESCRIPTION: Overtime Pay Period End Date FIELD DESCRIPTION: EDIT TYPE: DATE EDIT TYPE: LENGTH: 8 LENGTH: ALLOWABLE VALUES: Any valid date ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the pay period end date. DESCRIPTION: It must be entered at system initialization time. After system initialization, it is automatically updated by the day end batch processes. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 88 _________________________________________________________________ FIELD NAME: OT_SWITCH FIELD NAME: FIELD DESCRIPTION: Overtime Processing Switch FIELD DESCRIPTION: EDIT TYPE: LOGICAL EDIT TYPE: LENGTH: 1 LENGTH: ALLOWABLE VALUES: Y, N (yes, no) ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field turns overtime processing on or DESCRIPTION: off for your restaurant. If you do not pay overtime, set this to 'N'. If you do, set this switch to 'Y'. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 89 _________________________________________________________________ FIELD NAME: OV_UN_AMT FIELD NAME: FIELD DESCRIPTION: Employee Over / Under Amount FIELD DESCRIPTION: EDIT TYPE: MONEY EDIT TYPE: LENGTH: x LENGTH: ALLOWABLE VALUES: Any positive or negative dollar amount ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field may be used for keeping a running DESCRIPTION: total amount of how much an employee may owe the restaurant or vice versa. This is a user field and may be used any way you see fit. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 90 _________________________________________________________________ FIELD NAME: PE_ST_DT FIELD NAME: PE_SP_DT FIELD DESCRIPTION: Period Start Date FIELD DESCRIPTION: Period Stop Date EDIT TYPE: DATE EDIT TYPE: LENGTH: 8 LENGTH: ALLOWABLE VALUES: Display only, used by internal processes. ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: These fields are used internally by the DESCRIPTION: programs which extract payroll records for export to a foreign system. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 91 _________________________________________________________________ FIELD NAME: PP_MINS_TD FIELD NAME: FIELD DESCRIPTION: Minutes Worked This Period FIELD DESCRIPTION: EDIT TYPE: INTEGER EDIT TYPE: LENGTH: 5 LENGTH: ALLOWABLE VALUES: Display only, used by internal processes. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: These fields are used internally by the DESCRIPTION: programs which calculate overtime. It should be set to zero when an employee is initially loaded into the system. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 92 _________________________________________________________________ FIELD NAME: PROCESS_1 through 5 FIELD NAME: FIELD DESCRIPTION: Process 1 through 5 FIELD DESCRIPTION: EDIT TYPE: LOGICAL EDIT TYPE: LENGTH: 1 LENGTH: ALLOWABLE VALUES: Display only, used by internal processes. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: These fields are used internally by the day DESCRIPTION: end processes and programs. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 93 _________________________________________________________________ FIELD NAME: RMS_PRG_1 through 5 FIELD NAME: FIELD DESCRIPTION: History File Purge Days FIELD DESCRIPTION: EDIT TYPE: INTEGER EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: 0 through 9999 ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: These fields store the number of days before DESCRIPTION: data is purged from the history files. Setting the fields at 0 prevents any data from being purged from the file. Field Name Field Description Recommended Field Name Field Description Recommended Setting Setting RMS_PRG_1 Coupon History Purge Days 375 RMS_PRG_2 Activity Summary Purge Days 375 RMS_PRG_3 Hourly Labor History Purge Days 375 RMS_PRG_4 Time Record History Purge Days 45 RMS_PRG_5 Reserved for future use 0 Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 94 _________________________________________________________________ FIELD NAME: STD_PAY FIELD NAME: FIELD DESCRIPTION: Standard Pay FIELD DESCRIPTION: EDIT TYPE: MONEY EDIT TYPE: LENGTH: 6.2 LENGTH: ALLOWABLE VALUES: Display only, calculated field ALLOWABLE VALUES: ASSOCIATED TABLES: EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: These fields store the amount of regular pay DESCRIPTION: associated with an employee's time record. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 95 _________________________________________________________________ FIELD NAME: ST_HRS FIELD NAME: FIELD DESCRIPTION: Standard Hour Hours Worked FIELD DESCRIPTION: EDIT TYPE: Numeric EDIT TYPE: LENGTH: 7.2 LENGTH: ALLOWABLE VALUES: Display only field, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: ACTSUM ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the total standard hours DESCRIPTION: used to operate the store for a given day and activity code. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 96 _________________________________________________________________ FIELD NAME: ST_MINS_WK FIELD NAME: FIELD DESCRIPTION: Standard Minutes Worked FIELD DESCRIPTION: EDIT TYPE: Numeric EDIT TYPE: LENGTH: 4 LENGTH: ALLOWABLE VALUES: Display only field, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: EMPTIME, EMPTIMEH ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the total standard minutes DESCRIPTION: worked on a given time record. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 97 _________________________________________________________________ FIELD NAME: STORE_DATE FIELD NAME: FIELD DESCRIPTION: Store Date FIELD DESCRIPTION: EDIT TYPE: DATE EDIT TYPE: LENGTH: 8 LENGTH: ALLOWABLE VALUES: Any valid date ALLOWABLE VALUES: ASSOCIATED TABLES: ACTSUM, CUPONHST, EMPTIME, EMPTIMEH, ASSOCIATED TABLES: LABORHST, STORE ASSOCIATED INDEXES: ACTSUM1, ACTSUM2, EMPTIME, EMPTIMEH, ASSOCIATED INDEXES: CUPONHST, LABORHST DESCRIPTION: This is an important field in the system. DESCRIPTION: All history data is based on store date. All time records are entered for a store date. Each day end process is for a store date. When the system is first installed, set store date to the date which you want to start processing for using function SYSTEM SETUP. After that, this field is maintained automatically by the day end process. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 98 _________________________________________________________________ FIELD NAME: STORE_NO FIELD NAME: FIELD DESCRIPTION: Store Number FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 10 LENGTH: ALLOWABLE VALUES: Any valid text ALLOWABLE VALUES: ASSOCIATED TABLES: STORE ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: none DESCRIPTION: This is a user defined field. DESCRIPTION: Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 99 _________________________________________________________________ FIELD NAME: ST_PAY FIELD NAME: FIELD DESCRIPTION: Standard Pay FIELD DESCRIPTION: EDIT TYPE: MONEY EDIT TYPE: LENGTH: 8.2 LENGTH: ALLOWABLE VALUES: Display only field, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: ACTSUM ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the total standard pay for DESCRIPTION: a given day for a given activity. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 100 _________________________________________________________________ FIELD NAME: TOT_HRS FIELD NAME: FIELD DESCRIPTION: Total Hours FIELD DESCRIPTION: EDIT TYPE: NUMERIC EDIT TYPE: LENGTH: 7.2 LENGTH: ALLOWABLE VALUES: Display only field, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: ACTSUM ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the total hours worked for DESCRIPTION: a given day for a given activity. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 101 _________________________________________________________________ FIELD NAME: TOT_PAY FIELD NAME: FIELD DESCRIPTION: Total Pay FIELD DESCRIPTION: EDIT TYPE: MONEY EDIT TYPE: LENGTH: 8.2 LENGTH: ALLOWABLE VALUES: Display only field, calculated amount. ALLOWABLE VALUES: ASSOCIATED TABLES: ACTSUM ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field stores the total wages for a given DESCRIPTION: day for a given activity. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 102 _________________________________________________________________ FIELD NAME: USER_TEXT1 FIELD NAME: USER_TEXT2 FIELD DESCRIPTION: User Text 1 and 2 FIELD DESCRIPTION: EDIT TYPE: CHAR EDIT TYPE: LENGTH: 30 LENGTH: ALLOWABLE VALUES: Any character data ALLOWABLE VALUES: ASSOCIATED TABLES: EMPMASTR ASSOCIATED TABLES: ASSOCIATED INDEXES: none ASSOCIATED INDEXES: DESCRIPTION: This field may be used for storing any data DESCRIPTION: on an employee. Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 103 _________________________________________________________________ Labor Activity Report Page 1 For Feb/15/92 thru Feb/22/92 Activity - CK - COOK / CHEF STORE REGULAR OVERTIME LUNCH TOTAL DATE HOURS PAY HOURS PAY HOURS PAY HOURS PAY --------- ------------ ------------ ------------- -------------- Feb/15/92 12.60 88.20 0.00 0.00 4.00 28.00 12.60 88.20 Feb/16/92 11.00 77.00 0.00 0.00 4.00 28.00 11.00 77.00 Feb/17/92 12.45 87.15 0.00 0.00 4.00 28.00 12.45 87.15 Feb/18/92 11.50 80.50 0.00 0.00 4.00 28.00 11.50 80.50 Feb/19/92 14.00 98.00 0.00 0.00 4.00 28.00 14.00 98.00 Feb/20/92 11.05 77.35 0.00 0.00 4.00 28.00 11.05 77.35 Feb/21/92 7.00 49.00 6.25 65.63 4.00 28.00 13.25 114.63 --------- ------------ ------------ ------------- -------------- Total: 80.00 557.20 6.25 65.63 32.00 196.00 86.25 622.83 ============ ============ ============= ============== . . . . OTHER ACTIVITY CODES . . . . ============== ============ ============= ============== Grand: 200.19 1245.84 0.00 0.00 48.34 382.50 200.19 1245.84 ============== ============ ============= ============== Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 104 _________________________________________________________________ Coupon History Detail Report Page 1 Feb/01/92 thru Feb/15/92 STORE DATE AREA CODE COUPONS HUNG DROP COST COST PER COUPON Feb/01/92 NE 100 22.50 0.2250 Feb/04/92 NW 80 20.33 0.2541 Feb/06/92 SE 95 22.38 0.2356 Feb/07/92 SW 115 22.88 0.1990 Feb/12/92 NE 90 24.08 0.2676 Feb/14/92 SW 105 22.62 0.2154 -------- -------- -------- Totals: 585 134.79 0.2304 Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 105 _________________________________________________________________ Daily Labor Detail Report Page 1 For Feb/18/92 CK - COOK / CHEF Direct Labor Hours Emp No Time In Time Out Total Hours Labor Cost 4 900 1430 5.50 27.50 4 1500 2100 6.00 30.00 -------- -------- Totals for CK: 11.50 57.50 ======== ======== DW - DISHWASHING Direct Labor Hours Emp No Time In Time Out Total Hours Labor Cost 1 1300 2300 10.00 50.00 -------- -------- Totals for DW: 10.00 50.00 ======== ======== WA - TABLE WAITING Direct Labor Hours Emp No Time In Time Out Total Hours Labor Cost 3 900 1500 6.00 60.00 5 1100 1300 2.00 12.00 2 1430 2300 8.50 85.00 -------- -------- Totals for WA: 16.50 157.00 ======== ======== Grand Totals: 38.00 264.50 ======== ======== Copyright (C) 1989-1991 Restaurant Management Systems DATA DICTIONARY 106 _________________________________________________________________ Shift Sheet Report Page 1 DR - Drivers / Delivery Personnel Direct Labor Hours For Mar/08/92 Hour Average Mar/01 Feb/23 Feb/16 Feb/09 Mar/10/91 8- 9 _______ 0.56 0.60 0.50 0.55 0.45 0.70 9-10 _______ 1.98 1.80 2.00 2.00 1.90 2.20 10-11 _______ 2.00 2.00 2.00 2.00 2.00 2.00 11-12 _______ 4.17 3.40 4.24 4.40 4.00 4.80 12-13 _______ 5.02 4.60 5.00 5.00 5.00 5.50 13-14 _______ 4.22 3.50 4.10 4.30 4.20 5.00 14-15 _______ 2.08 2.00 2.00 2.04 2.00 2.00 15-16 _______ 2.00 2.00 2.00 2.00 2.00 2.00 16-17 _______ 2.50 2.20 2.40 2.60 2.45 2.85 17-18 _______ 3.38 3.10 3.24 3.35 3.42 3.80 18-19 _______ 4.37 4.02 4.30 4.40 4.32 4.80 19-20 _______ 4.06 4.00 4.00 4.00 4.00 4.30 20-21 _______ 3.34 3.30 3.50 3.23 3.43 3.25 21-22 _______ 1.38 1.40 1.30 1.56 1.43 1.22 ------ ------ ------ ------ ------ ------- Total Hours: 41.06 37.92 40.58 41.43 40.60 44.22 ------ ------ ------ ------ ------ ------- Total Wages: 151.68 162.32 165.72 162.40 177.68 ======= ======= ======= ======= ======= Copyright (C) 1989-1991 Restaurant Management Systems BROWSE QUICK REFERENCE 107 _________________________________________________________________ The commands can also be initiated by pressing the command key along with the <ALT> key. Command Name Command Key Description Add Blank A Add a blank record Bottom B Move to the bottom database record Add Copy C Add a record by copying the current record. Delete Record D Mark the current record for deletion Edit E Switch to the edit screen if possible Find F Find a record Help H Display the help screen Modify Record M Modify the current record Record R Enter a record to move to Select Record Ordering Index S Select a record ordering index Top T Move to the top database record Undelete Record U Remove the deletion mark from the current record Browse Z Switch to the browse screen if possible Exit X Exit Page Up <Pg Up> Move up one screen of records Page Down <Pg Dn> Move down one screen of records Up <Up> Move to the next record Down <Down> Move to the previous record Copyright (C) 1989-1991 Restaurant Management Systems DAILY OPERATIONAL PROCEDURE CHECKLIST 108 _________________________________________________________________ 1) Verify that all reference tables are up to date and loaded. - Add any new employees to the system. - Terminate any employees who are no longer employed with the restaurant. - The Activity Table, Coupon Drop Area Code Table and Employee Type Table will not require frequent maintenance after the system is operational. 2) Enter all time transactions for the day. 3) Perform Daily Batch Process. 4) Generate the appropriate reports for your restaurant. 5) Perform Database Backup -- Daily. 6) Perform System Backup -- Weekly. Copyright (C) 1989-1991 Restaurant Management Systems ERROR MESSAGES 109 _________________________________________________________________ APPLICATION ERRORS Employee 99999999 not found in table EMPMASTR. Calculations for this employee will be incomplete. An employee has been deleted out of the Employee Master table after time records have been posted and before dayend has been run. Re-enter employee and rerun dayend. Error Copying file FILENAME into FILENAME. The dayend batch process cannot copy files. Error Loading Pay Period begin date Check the PAY PERIOD BEGIN DATE field using the System Setup function. Error Loading Store Date from table STORE. Check the STORE DATE field using the System Setup function. Fatal error opening file FILENAME. This error occurs if the application programs cannot find the databases. Check the RMSDATA statement in the "AUTOEXEC.BAT" file. Illegal Date An invalid date has been entered. Correctly enter a valid date or press escape <ESC> to cancel all changes. Record Not Found This message is generated when the find information was not found. This error occurs only if there are no records after the find information. Copyright (C) 1989-1991 Restaurant Management Systems ERROR MESSAGES 110 _________________________________________________________________ DISK DRIVE ERRORS 100 Error Creating a File This error could be caused by a full directory or disk problem. Insufficient rights on a network drive or an illegal file name. 120 Error Opening a File This problem may be caused by accessing databases which have inadvertently been erased. This problem may also have been caused if "FILES=20" or greater is not in the "CONFIG.SYS" file. If you have run other software products before running EZTIME and you get this error, try rebooting. 140 Error Reading from a File This error may occur during a disk drive failure. 160 Error Writing to a File This error occurs when the disk is full. 180 Error Closing a File Unsuccessful file close. Index Errors 300 Error Building an Index File Insufficient memory. 330 Database and Index are out of sync. This error will occur if databases are updated without updating the associated index files. 335 Same as 330. Copyright (C) 1989-1991 Restaurant Management Systems ERROR MESSAGES 111 _________________________________________________________________ 340 Key is not unique Certain index files have been created as unique. This means each key value in the index must be unique. An attempt to add a second key with the same value causes this error. For example; each employee must have a unique employee number. If you try to give the same employee number to two or more employees, you will get this message. 380 Seek on Database with no Index File An index file may have inadvertently been deleted. CRITICAL ERRORS 900 Out of Memory Condition. All memory available has been used, more required. Try rebooting. 920 Memory Allocation All memory available has been used, more required. Try rebooting. Copyright (C) 1989-1991 Restaurant Management Systems ORDER FORM 112 _________________________________________________________________ Restaurant Management Systems P.O. Box 171472 Irving, TX 75017-1472 Telephone (214) 986-6581 PRICE PRICE DESCRIPTION QUANTITY EACH EXTENDED ----------------------------------------------------------------- Registered Copy of EZTIME Single User License _____ $99.00 $_______ Network License _____ $149.00 $_______ Subtotal: $_______ Postage and Handling $5.00 $_______ Texas residents add 8.25 State Sales Tax $_______ Total: $_______ Please make checks payable to : Restaurant Management Systems (U.S. funds only) Ship to address: Name ________________________________________________________ Address ________________________________________________________ ________________________________________________________ City _________________________ State _________ Zip Code ________ Copyright (C) 1989-1991 Restaurant Management Systems REQUEST TO BE PUT ON MAILING LIST 113 _________________________________________________________________ If you have received this program from a User's Group or a friend and would like to be put on RMS's mailing list so that you will receive information on upcoming releases and notification of new products, please fill in your name and address below and send to: Restaurant Management Systems P.O. Box Irving Texas, 75060 Name ________________________________________________________ Address ________________________________________________________ ________________________________________________________ City _________________________ State _________ Zip Code ________ Copyright (C) 1989-1991 Restaurant Management Systems CUSTOMER FEEDBACK 114 _________________________________________________________________ RMS is committed to providing useful software to the food service industry. Any input you would care to give concerning any of our products, or new product ideas, would be appreciated. If you have any ideas or comments that would make them better programs, please let us know. We are working hard to make RMS software products the best, most useful, and affordable products of their kind on the market today. Your input is very valuable input toward achieving that goal. ________________________________________________________________ ________________________________________________________________ _________________________________________________________________ _________________________________________________________________ _________________________________________________________________ _________________________________________________________________ _________________________________________________________________ _________________________________________________________________ _________________________________________________________________ _________________________________________________________________ Please use additional sheets if required. Check Here If you would like to be a Beta Site: ___ Copyright (C) 1989-1991 Restaurant Management Systems